Context parameters and identifiers for communication

ABSTRACT

In one aspect, a method related to communication. In addition, other method, system, and program product aspects are described in the claims, drawings, and/or text forming a part of the present application.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is related to and claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC §119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Related Application(s)).

Related Application

-   -   For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation of U.S. patent        application Ser. No. 14/875,046, entitled “Context Parameters        and Identifiers for Communication”, filed Oct. 5, 2015, which is        a continuation of U.S. patent application Ser. No. 11/645,219,        entitled “Context Parameters and Identifiers for Communication”,        filed Dec. 21, 2006, which is a continuation-in-part of U.S.        Pat. No. 8,346,872, entitled “Context Parameters and Identifiers        for Communication, issued Jan. 1, 2013, which is va        continuation-in-part of U.S. patent application Ser. No.        11/480,773, entitled “Usage Parameters for Communication        Content”, filed Jun. 30, 2006, the entirety of which are hereby        incorporated by reference.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation or continuation-in-part. Stephen G. Kunin, Benefit ofPrior-Filed Application, USPTO Official Gazette Mar. 18, 2003, availableat http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm.The present applicant entity has provided above a specific reference tothe application(s) from which priority is being claimed as recited bystatute. Applicant entity understands that the statute is unambiguous inits specific reference language and does not require either a serialnumber or any characterization, such as “continuation” or“continuation-in-part,” for claiming priority to U.S. patentapplications. Notwithstanding the foregoing, applicant entityunderstands that the USPTO's computer programs have certain data entryrequirements, and hence applicant entity is designating the presentapplication as a continuation-in-part of its parent applications as setforth above, but expressly points out that such designations are not tobe construed in any way as any type of commentary and/or admission as towhether or not the present application contains any new matter inaddition to the matter of its parent application(s).

All subject matter of the Related Applications and of any and allparent, grandparent, great-grandparent, etc. applications of the RelatedApplications is incorporated herein by reference to the extent suchsubject matter is not inconsistent herewith.

TECHNICAL FIELD

The present application relates, in general, to communication.

SUMMARY

In one aspect, a method related to communication includes but is notlimited to storing a communications context parameter associated with acommunications context; and storing a communications context identifierassociated with the communications context. In addition to theforegoing, other method aspects are described in the claims, drawings,and text forming a part of the present application.

In one aspect, a system related to communication includes but is notlimited to circuitry for storing a communications context parameterassociated with a communications context; and circuitry for storing acommunications context identifier associated with the communicationscontext. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent application.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming and/or electro-mechanicaldevices and/or optical devices for effecting the herein-referencedmethod aspects; the circuitry and/or programming and/orelectromechanical devices and/or optical devices can be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein-referenced method aspects depending upon the design choicesof the system designer skilled in the art.

In one aspect, a program product includes but is not limited to a signalbearing medium bearing one or more instructions for storing acommunications context parameter associated with a communicationscontext; and one or more instructions for storing a communicationscontext identifier associated with the communications context. Inaddition to the foregoing, other program product aspects are describedin the claims, drawings, and text forming a part of the presentapplication.

In addition to the foregoing, various other method, system, and/orprogram product aspects are set forth and described in the teachingssuch as the text (e.g., claims and/or detailed description) and/ordrawings of the present application.

The foregoing is a summary and thus contains, by necessity,simplifications, generalizations and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is NOT intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matter described herein will become apparent in theteachings set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 depicts an exemplary environment in which the methods and systemsdescribed herein may be represented;

FIG. 2 depicts a high-level logic flowchart of an operational process;

FIGS. 3A-3B depict several alternative implementations of the high-levellogic flowchart of FIG. 2;

FIG. 4 depicts several alternative implementations of the high-levellogic flowchart of FIGS. 3A-3B;

FIGS. 5A-5B depict several alternative implementations of the high-levellogic flowchart of FIG. 2;

FIG. 6 depicts several alternative implementations of the high-levellogic flowchart of FIGS. 5A-5B;

FIG. 7 depicts a high-level logic flowchart of an operational process;

FIGS. 8A-8B depict several alternative implementations of the high-levellogic flowchart of FIG. 7;

FIG. 9 depicts a high-level logic flowchart of an operational process;and

FIG. 10 depicts several alternative implementations of the high-levellogic flowchart of FIG. 9.

The use of the same symbols in different drawings typically indicatessimilar or identical items.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

FIG. 1 depicts an exemplary environment in which the methods and systemsdescribed herein may be represented.

In the exemplary environment 100, the origin entity 102 may be a personand/or an entity capable of communicating with other persons and/orentities. The origin entity 102 may include but is not limited to asingle person, a group of two or more persons associated for the purposeof a communication (e.g., a group of three persons communicating withanother person and/or group of persons to arrange a social gathering),and/or a one or more persons of a group of persons associated for one ormore purposes or reasons (e.g., an employee or employees of acorporation, or members of a family) some or all of whom may participatein a communication on behalf of the association.

The target entity 104 may be a person and/or an entity capable ofcommunicating with other persons and/or entities. The target entity 104may include but is not limited to a single person, a group of two ormore persons associated for the purpose of a communication (e.g., agroup of three persons communicating with another person and/or group ofpersons to arrange a social gathering), and/or a one or more persons ofa group of persons associated for one or more purposes or reasons (e.g.,an employee or employees of a corporation, or members of a family) someor all of whom may participate in a communication on behalf of theassociation.

A communication or other event may take place between the origin entity102 and the target entity 104 that prompts the origin entity 102 toselect a communications context for communications with the targetentity 104. Such communication may take place using means including butnot limited to telephony (using the public switched telephone system,the internet (via, e.g., Voice over Internet Protocol (“VoIP”), orboth), instant and/or text messaging, and/or electronic mail (“email”).Systems 106 represent any systems that have one or more communicationsdevices including but not limited to a telephone, a VoIP endpoint, acomputer running email and/or instant messaging software, and/or apersonal digital assistant and/or a cell phone running text messagingsoftware. The systems 106 are illustrated in the exemplary environment100 in close physical proximity to the origin entity 102 and the targetentity 104. Those skilled in the art will appreciate that one or more ofthe devices included in the systems 106 may be relatively distant butoperably coupled to one or more devices included in the systems 106 andin physical proximity to the respective entities with which the systems106 are associated (e.g., origin entity 102 and/or the target entity104). The systems 106 may be operably coupled via some network orcombinations of networks (e.g. the internet, a wireless network, anintranet, etc.), represented in the exemplary environment 100 by thenetwork 108, and/or by public switched telephone network (“PSTN”)devices represented by the PSTN system 110, and/or or by somecombination of the network 108 and the PSTN 110. The operable couplingsbetween the systems 106 may be tangible connections (e.g., wires and/orcables and/or fiber-optic lines), or intangible connections (e.g.,wireless connections, e.g., radio-frequency connections between cellphone and cell network towers), and/or some combination of tangibleconnections and intangible connections.

The communications context may be defined in part by one or morecommunications context parameters, which may be associated with therelevant communications context. A communications context parameter mayinclude but not be limited to one or more target entity parametersassociated with a location of the target entity 104, a system associatedwith the target entity 104, and/or an identity of the target entity 104.For example, a communications context parameter may include but not belimited to one or more target entity parameters associated with (a) alocation, such as the location at which the origin entity 102 met thetarget entity 104 and/or the location of the target entity 104 when theorigin entity 102 and the target entity 104 first communicated, e.g., abusiness meeting or a social gathering, and/or one or more likelylocations of the target entity 104 when further communications takeplace; (b) a system associated with the target entity 104 which thetarget entity 104 may use in communications with the origin entity 102,e.g., a telephone or a VoIP endpoint; or (c) an identity of the targetentity 104, e.g., a name and/or nickname and/or code name and/or role(e.g., administrative assistant, salesman, engineer, etc.) of the targetentity 104, a telephone number associated with the target entity 104, anInternet Protocol (“IP”) address associated with a system associatedwith the target entity 104, and/or an electronic mail address associatedwith the target entity 104.

A communications context parameter may also include but not be limitedto one or more indications of a relationship between the origin entity102 and the target entity 104, e.g., business, family, social: one ormore indications of a relative priority of communications between theorigin entity 102 and the target entity 104, e.g., as compared withcommunications between the origin entity 102 and other parties besidesthe target entity 104, e.g., during business hours, communications withbusiness associates are more important than communications with thetarget entity 104, a social contact, but during non-business hours,communications with the target entity 104 are more important thancommunications with business associates.

A communications context parameter may be stored using the memoryresources and/or hardware and/or software and/or firmware(“hardware/software/firmware”) of the system 106 associated with theorigin entity 102 and/or memory resources and/orhardware/software/firmware operably coupled to the system 106 associatedwith the origin entity 102.

A communications context parameter may be fictional or real. Acommunications context parameter may be created from one or more of anumber of sources or methods, including but not limited to random orpseudo-random generation or selection from a database. Within thecommunications context, the origin entity 102 may wish communicationswith the target identity 104 to be identified by one or more of thecommunications context parameters, e.g., to have one or more of thecommunications context parameters displayed using a calleridentification feature associated with a system associated with theorigin entity 102. Display of one or more selected real communicationscontext parameters or one or more fictional communications contextparameters may be desirable in a given communications context, e.g., forpurposes of communications security and/or deception of personsproximate to or associated with the origin entity 102. For example, if acommunication within a given communications context is a telephone callfrom the origin entity 102 to the target entity 104, a real or fictionalcommunications context parameter including a target entity parameterassociated with a false telephone number and/or a false name may giverise to a display feature via a user interface of a system 106associated with the origin entity 102, e.g., text or graphics on theuser interface system, for, e.g., verification of the communicationscontext parameter, via text and/or graphics on a user interface of asystem 106 associated with the origin entity 102, by the origin entity102 and/or deception of persons proximate to or associated with theorigin entity 102.

Within the communications context, the origin entity 102 may wish to beidentified by one or more origin entity parameters associated with therelevant communications context and associated with (a) a location, suchas an actual location of the origin entity 102 during a communicationwith the target entity 102 or a location (fictional or real) at whichthe origin entity is not located during a communication with the targetentity 104 (e.g., for purposes of communications security during aconfidential activity in which the origin entity 102 is involved, and/orfor purposes of deception of the target entity 104 and/or of personsand/or entities proximate to or associated with the target entity 104);(b) a system (fictional or real) that is associated with the originentity 102 or that the origin entity wishes the target entity 104 and/orpersons proximate to or associated with the target entity 104 to believeis associated with the target entity 102 (e.g., for purposes ofcommunications security during a confidential activity in which theorigin entity 102 is involved, or for purposes of deception); or (c) anidentity (fictional or real) that is associated with the origin entity102 or that the origin entity wishes the target entity 104 and/orpersons proximate to or associated with the target entity 104 to believeis associated with the target entity 102 (e.g., for purposes ofcommunications security during a confidential activity in which theorigin entity 102 is involved, or for purposes of deception), e.g., aname and/or nickname and/or code name of the origin entity 102, atelephone number nominally associated with the origin entity 102, an IPaddress associated with a system nominally associated with the originentity 102, and/or an electronic mail address nominally associated withthe origin entity 102.

A communications context identifier may be created from one or more of anumber of sources or methods, including but not limited to random orpseudo-random generation or selection from a database.

A communications context identifier may be stored using the memoryresources and/or hardware/software/firmware of the system 106 associatedwith the origin entity 102 and/or memory resources and/orhardware/software/firmware operably coupled to the system 106 associatedwith the origin entity 102.

A communications context identifier may be transmitted in conjunctionwith a communication within the communications context. For example, ifthe communications within the communications context is a telephone callreply from the origin entity 102 to the target entity 104 to a telephonecall from the target entity 104 to the origin entity 102, acommunications context identifier including an origin entity parameterassociated with a false telephone number and/or a false name may betransmitted in conjunction with the reply telephone call, such that thefalse telephone number and false name, both associated with the originentity 102, appear on a caller identification feature of the telephoneof the target entity 104. Further, a communications context identifiermay give rise to a display feature in conjunction with a communicationwithin the communications context. For example, if the communicationwithin the communications context is a VoIP call from the origin entity102 to the target entity 104, a communications context identifierincluding an origin entity parameter associated with a false telephonenumber and/or a false name may be displayed in conjunction with the VoIPcall, e.g., via text and/or graphics on a user interface of a system 106associated with the origin entity 102, for purposes, e.g., ofverification that the communications context identifier beingtransmitted to a target entity 104 is the communications contextidentifier desired by the origin entity 102.

Following are a series of flowcharts depicting implementations ofprocesses. For ease of understanding, the flowcharts are organized suchthat the initial flowcharts present implementations via an overall “bigpicture” viewpoint and thereafter the following flowcharts presentalternate implementations and/or expansions of the “big picture”flowcharts as either sub-steps or additional steps building on one ormore earlier-presented flowcharts. Those having skill in the art willappreciate that the style of presentation utilized herein (e.g.,beginning with a presentation of a flowchart(s) presenting an overallview and thereafter providing additions to and/or further details insubsequent flowcharts) generally allows for a rapid and easyunderstanding of the various process implementations. In addition, thoseskilled in the art will further appreciate that the style ofpresentation used herein also lends itself well to modular and/orobject-oriented program design paradigms.

FIG. 2 depicts a high-level logic flowchart of an operational process.The illustrated process may include operation 200 and/or operation 202.

Operation 200 shows storing a communications context parameterassociated with a communications context. Operation 200 may include, forexample, storing a communications context parameter associated with acommunications context such as a name of a target entity 104 (e.g., anickname or a code name), a location associated with the target entity104 (e.g., a home, a wife's office, or a lovers' hideaway), and/or asystem associated with the target entity 104 (e.g., a cell phone or acomputer at a home), where the communications context parameter isassociated with a communications context such as a context in whichcommunications (e.g., phone calls, instant and/or text messaging, and/oremails) may be conducted with a person or entity (e.g., a spouse, abusiness partner, a lover, and/or an investigation subject). Thiscontext may include but is not limited to one or more situations inwhich an origin entity 102 may communicate with a target entity 104where the origin entity 102 may wish to exercise discretion (e.g., for aconfidential communication) and/or deception of the target entity 104and/or of persons and/or entities proximate to or associated with thetarget entity 104 (e.g., for a communication with a lover, or aninvestigation subject such as a crime suspect where the origin entity isa policeman).

The storing of operation 200 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 202 illustrates storing a communications context identifierassociated with the communications context. Operation 202 may include,for instance, storing a communications context identifier associatedwith the communications context such as a name of the origin entity 102(e.g., a nickname or code name), a location associated with the originentity 102 (e.g., a home of a person associated with the origin entity102, the office of the origin entity 102), and/or a system associatedthe origin entity 102 (e.g., a personal computer used for VoIP calls bythe origin entity 102, or the cell phone of the origin entity 102),where the communications context parameter is associated with acommunications context such as a context in which communications (e.g.,phone calls, instant and/or text messaging, and/or emails) may beconducted with a person or entity (e.g., a boyfriend and/or girlfriend,a business associate, a lover, and/or an investigation subject). Thiscontext may include but is not limited to one or more situations inwhich an origin entity 102 may communicate with a target entity 104where the origin entity 102 may wish to exercise discretion (e.g., for aconfidential communication) and/or deception of the target entity 104and/or of persons and/or entities proximate to or associated with thetarget entity 104 (e.g., for a communication with a negotiating partnerin a concealed business deal, or an investigation subject such as acrime suspect where the origin entity is a policeman).

The storing of operation 202 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

FIGS. 3A-3B depicts several alternative implementations of thehigh-level logic flowchart of FIG. 2. Operation 200—storing acommunications context parameter associated with a communicationscontext—may include one or more of the following operations: 300, 302,304, 306, 308, 310, and/or 312.

Operation 300 shows storing the communications context parameter,wherein the communications context parameter includes a target entityparameter associated with a location associated with a target entity.Operation 300 may include, for example, storing the communicationscontext parameter, wherein the communications context parameter includesa target entity parameter associated with a location associated with atarget entity, where the target entity parameter is associated with alocation associated with a target entity 104, such as the home of thetarget entity 104, the office of the target entity 104, some locationfrequented by the target entity 104, or a location designated as thelocation from which the target entity 104 is to communicate with theorigin entity 102. The location may be a location at which the targetentity 104 may actually be located or a location at which the targetentity 104 may not actually be located but which is associated with thetarget entity 104 for purposes of confidentiality and/or deception,including a fictitious location.

The storing of operation 300 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 302 illustrates storing the communications context parameter,wherein the communications context parameter includes a target entityparameter associated with a system associated with the target entity.Operation 302 may include, for example, storing the communicationscontext parameter, wherein the communications context parameter includesa target entity parameter associated with a system associated with thetarget entity, where the target entity parameter is associated with asystem 106 associated with a target entity 104, such as a personalcomputer that the target entity 104 uses to make VoIP calls, a cellphone of the target entity 104, a computer from which the target entitysends and receives emails, or the personal digital assistant with whichthe target entity 104 sends and receives text messages.

The storing of operation 302 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 304 depicts storing the communications context parameter,wherein the communications context parameter includes a target entityparameter associated with an identity of a target entity. Operation 304may include, for instance, storing the communications context parameter,wherein the communications context parameter includes a target entityparameter associated with an identity of a target entity, where thetarget entity parameter is associated with an identity of a targetentity 104, such as a name and/or a nickname and/or a code name and/oran alphanumeric designator that serves to distinguish the target entity104 from other entities. The target entity parameter associated with anidentity of the target entity 104 may be real, e.g., a real name of thetarget entity 104, or fictional, e.g., an assumed name or a namedesigned to deceive and/or mislead, and/or some alphanumericdesignation.

The storing of operation 304 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 306 depicts storing the communications context parameter,wherein at least a portion of the communications context parameter israndomly generated. Operation 306 may include, for instance, storing thecommunications context parameter, wherein at least a portion of thecommunications context parameter is randomly generated, such as a partof a target entity parameter included in a communications contextparameter that is the output of a computational process that generates arandom number that is used to generate a random name and/or a randomalphanumeric designator.

The storing and/or the random generating of operation 306 may beperformed, e.g., upon initiation by the origin entity 102 and/or uponinitiation by automated action of hardware/software/firmware of a system106 associated with the origin entity 102 and/or byhardware/software/firmware of a system and/or systems operably coupledto the system 106 associated with the origin entity 102, using memoryresources of the system 106 associated with the origin entity 102 and/orthe memory resources of a system and/or systems associated with thesystem 106 associated with the origin entity 102.

Operation 308 depicts storing the communications context parameter,wherein at least a portion of the communications context parameter ispseudo-randomly generated. Operation 308 may include, for instance,storing the communications context parameter, wherein at least a portionof the communications context parameter is pseudo-randomly generated,such as a part of a target entity parameter included in a communicationscontext parameter that is the output of a computational process thatgenerates a pseudo-random number that is used to generate apseudo-random name and/or a pseudo-random alphanumeric designator.

The storing and/or the pseudo-random generating of operation 308 may beperformed, e.g., upon initiation by the origin entity 102 and/or uponinitiation by automated action of hardware/software/firmware of a system106 associated with the origin entity 102 and/or byhardware/software/firmware of a system and/or systems operably coupledto the system 106 associated with the origin entity 102, using memoryresources of the system 106 associated with the origin entity 102 and/orthe memory resources of a system and/or systems associated with thesystem 106 associated with the origin entity 102.

Operation 310 illustrates storing the communications context parameter,wherein at least a portion of the target entity parameter is selectedfrom a database. Operation 310 may include, for instance, storing thecommunications context parameter, wherein at least a portion of thetarget entity parameter is selected from a database, such as a part of atarget entity parameter included in a communications context parameterthat is a selection from a database of possible names and/oralphanumeric designators. The selection may be based, e.g., on one ormore predetermined selection criteria and/or on random and/orpseudo-random selection.

The storing and/or the selection of operation 310 may be performed,e.g., upon initiation by the origin entity 102 and/or upon initiation byautomated action of hardware/software/firmware of a system 106associated with the origin entity 102 and/or byhardware/software/firmware of a system and/or systems operably coupledto the system 106 associated with the origin entity 102, using memoryresources of the system 106 associated with the origin entity 102 and/orthe memory resources of a system and/or systems associated with thesystem 106 associated with the origin entity 102.

Operation 312 shows storing the communications context parameter,wherein the communications context parameter may be displayed inconjunction with a communication in the communications context.Operation 312 may include, for example, storing the communicationscontext parameter, wherein the communications context parameter may bedisplayed in conjunction with a communication in the communicationscontext, where the communications context parameter may give rise to adisplay in conjunction with a communication between the target entity104 and the origin entity 102 on a display feature of a system 106associated with the origin entity 102, e.g., a code name associated withthe target entity 104 is displayed on the caller identification featureof a telephone of the origin entity 102 when the target entity 104places a telephone call to the telephone of the origin entity 102.

The storing and/or the display of operation 312 may be performed, e.g.,upon initiation by the origin entity 102 and/or upon initiation byautomated action of hardware/software/firmware of a system 106associated with the origin entity 102 and/or byhardware/software/firmware of a system and/or systems operably coupledto the system 106 associated with the origin entity 102, using memoryresources of the system 106 associated with the origin entity 102 and/orthe memory resources of a system and/or systems associated with thesystem 106 associated with the origin entity 102.

FIG. 4 depicts several alternative implementations of the high-levellogic flowchart of FIGS. 3A-3B. Operation 304—storing the communicationscontext parameter, wherein the communications context parameter includesa target entity parameter associated with an identity of a targetentity—may include one or more of the following operations: 400, 402,404, and/or 406.

Operation 400 shows storing the communications context parameter,wherein the target entity parameter includes a name associated with theidentity of the target entity. Operation 400 may include, for instance,storing the communications context parameter, wherein the target entityparameter includes a name associated with the identity of the targetentity, where the target entity parameter includes a real or fictitiousname and/or nickname and/or code name associated with a system 106,e.g., a telephone and/or personal computer and/or personal digitalassistant, associated with the target entity 104.

The storing of operation 400 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 402 illustrates storing the communications context parameter,wherein the target entity parameter includes a telephone numberassociated with the identity of the target entity. Operation 402 mayinclude, for example, storing the communications context parameter,wherein the target entity parameter includes a telephone numberassociated with the identity of the target entity, where the targetentity parameter includes a real or fictitious telephone numberassociated with a system 106, e.g., a telephone and/or personal computerand/or personal digital assistant, associated with the target entity104.

The storing of operation 402 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 404 depicts storing the communications context parameter,wherein the target entity parameter includes an Internet Protocoladdress associated with the identity of the target entity. Operation 404may include, for instance, storing the communications context parameter,wherein the target entity parameter includes an Internet Protocoladdress associated with the identity of the target entity, where thetarget entity parameter includes a real or fictitious Internet Protocoladdress associated with a system 106, e.g., a personal computer,associated with the target entity 104 and used by the target entity 104for VoIP calls and/or emailing and/or instant messaging.

The storing of operation 404 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 406 shows storing the communications context parameter,wherein the target entity parameter includes an electronic mail addressassociated with the identity of the target entity. Operation 406 mayinclude, for example, storing the communications context parameter,wherein the target entity parameter includes an electronic mail addressassociated with the identity of the target entity, where the targetentity parameter includes a real or fictitious email address associatedwith a target entity 104.

The storing of operation 406 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

FIGS. 5A-5B depicts several alternative implementations of thehigh-level logic flowchart of FIG. 2. Operation 202—storing acommunications context identifier associated with the communicationscontext—may include one or more of the following operations: 500, 502,504, 506, 508, 510, and/or 512.

Operation 500 illustrates storing the communications context identifier,wherein the communications context identifier includes an origin entityparameter associated with a location of an origin entity. Operation 500may include, for instance, storing the communications contextidentifier, wherein the communications context identifier includes anorigin entity parameter associated with a location of an origin entity,where the origin entity parameter is associated with a locationassociated with an origin entity 102, such as the office of the origin,some location frequented by the origin entity 102, and/or a locationdesignated by the target entity as a location from which the originentity 102 is to communicate with the target entity 104. The locationmay be a location at which the origin entity 102 may actually be locatedor a location at which the origin entity 102 may not actually be locatedbut which is associated with the origin entity 102 for purposes ofconfidentiality and/or deception, including a fictitious location.

The storing of operation 500 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 502 shows storing the communications context identifier,wherein the communications context identifier includes an origin entityparameter associated with a system of an origin entity. Operation 502may include, for instance, storing the communications contextidentifier, wherein the communications context identifier includes anorigin entity parameter associated with a system of an origin entity,where the origin entity parameter is associated with a system 106associated with an origin entity 102, such as a cell phone of the originentity 102, a personal computer that the origin entity 102 uses to makeVoIP calls, a computer from which the origin entity sends and receivesinstant messages. The system 106 may actually be a system 106 that maybe used by the origin entity 102 or a system 106 that may not actuallybe used by the origin entity 102 but is associated with the originentity 102 for purposes of confidentiality and/or deception, including afictitious system 106.

The storing of operation 502 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 504 depicts storing the communications context identifier,wherein the communications context identifier includes an origin entityparameter associated with an identity of an origin entity. Operation 504may include, for instance, storing the communications contextidentifier, wherein the communications context identifier includes anorigin entity parameter associated with an identity of an origin entity,where the origin entity parameter is associated with an identity of anorigin entity 102, such as a name and/or a nickname and/or a code nameand/or an alphanumeric designator that serves to distinguish the originentity 102 from other entities. The origin entity parameter associatedwith an identity of the origin entity 102 may be real, e.g., a real nameof the origin entity 104, or fictional, e.g., an assumed name or a namedesigned to deceive and/or mislead, and/or some alphanumericdesignation.

The storing of operation 504 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 506 depicts storing the communications context identifier,wherein at least a portion of the communications context identifier israndomly generated. Operation 506 may include, for instance, storing thecommunications context identifier, wherein at least a portion of thecommunications context identifier is randomly generated, such as a partof an origin entity parameter included in a communications contextparameter that is the output of a computational process that generates arandom number that is used to generate a random name and/or a randomalphanumeric designator.

The storing and/or the random generating of operation 506 may beperformed, e.g., upon initiation by the origin entity 102 and/or uponinitiation by automated action of hardware/software/firmware of a system106 associated with the origin entity 102 and/or byhardware/software/firmware of a system and/or systems operably coupledto the system 106 associated with the origin entity 102, using memoryresources of the system 106 associated with the origin entity 102 and/orthe memory resources of a system and/or systems associated with thesystem 106 associated with the origin entity 102.

Operation 508 shows storing the communications context identifier,wherein at least a portion of the communications context identifier ispseudo-randomly generated. Operation 508 may include, for instance,storing the communications context identifier, wherein at least aportion of the communications context identifier is pseudo-randomlygenerated, such as a part of an origin entity parameter included in acommunications context identifier that is the output of a computationalprocess that generates a pseudo-random number that is used to generate apseudo-random name and/or a pseudo-random alphanumeric designator.

The storing and/or the pseudo-random generating of operation 508 may beperformed, e.g., upon initiation by the origin entity 102 and/or uponinitiation by automated action of hardware/software/firmware of a system106 associated with the origin entity 102 and/or byhardware/software/firmware of a system and/or systems operably coupledto the system 106 associated with the origin entity 102, using memoryresources of the system 106 associated with the origin entity 102 and/orthe memory resources of a system and/or systems associated with thesystem 106 associated with the origin entity 102.

Operation 510 depicts storing the communications context identifier,wherein at least a portion of the communications context identifier isselected from a database. Operation 510 may include, for instance,storing the communications context identifier, wherein at least aportion of the communications context identifier is selected from adatabase, such as a part of an origin entity parameter included in acommunications context identifier that is a selection from a database ofpossible names and/or alphanumeric designators. The selection may bebased, e.g., on one or more predetermined selection criteria and/or onrandom and/or pseudo-random selection.

The storing and/or the selection of operation 510 may be performed,e.g., upon initiation by the origin entity 102 and/or upon initiation byautomated action of hardware/software/firmware of a system 106associated with the origin entity 102 and/or byhardware/software/firmware of a system and/or systems operably coupledto the system 106 associated with the origin entity 102, using memoryresources of the system 106 associated with the origin entity 102 and/orthe memory resources of a system and/or systems associated with thesystem 106 associated with the origin entity 102.

Operation 512 illustrates storing the communications context identifier,wherein the communications context identifier may be transmitted inconjunction with a communication in the communications context.Operation 512 may include, for example, storing the communicationscontext identifier, wherein the communications context identifier may betransmitted in conjunction with a communication in the communicationscontext, where the communications context identifier may be transmittedin conjunction with a communication between the origin entity 102 andthe target entity 104 and may give rise to a display feature of a system106 associated with the target entity 104, e.g., a code name associatedwith the origin entity 102 may be displayed on the caller identificationfeature of a telephone of the target entity 104 when the origin entity102 places a telephone call to the telephone of the target entity 104 inconjunction with the code name of the origin entity 102. Further, thecommunications context identifier that may be transmitted in conjunctionwith the communications context may give rise to a display feature of asystem 106 associated with the origin entity 102, e.g., initiating thedisplay of text and/or graphics on a display system of a system 106associated with the origin entity 102, for purposes of, e.g., verifyingthe communications context identifier that may be transmitted, and/orinforming and/or deceiving entities proximate to or associated with theorigin entity 102.

The storing and/or the transmission of operation 512 may be performed,e.g., upon initiation by the origin entity 102 and/or upon initiation byautomated action of hardware/software/firmware of a system 106associated with the origin entity 102 and/or byhardware/software/firmware of a system and/or systems operably coupledto the system 106 associated with the origin entity 102, using memoryresources of the system 106 associated with the origin entity 102 and/orthe memory resources of a system and/or systems associated with thesystem 106 associated with the origin entity 102.

FIG. 6 depicts several alternative implementations of the high-levellogic flowchart of FIGS. 5A-5B. Operation 504—storing the communicationscontext identifier, wherein the communications context identifierincludes an origin entity parameter associated with an identity of anorigin entity—may include operations 600, 602, 604, and/or 606.

Operation 600 shows storing the communications context identifier,wherein the origin entity parameter includes a name associated with theidentity of the origin entity. Operation 600 may include, for instance,storing the communications context identifier, wherein the origin entityparameter includes a name associated with the identity of the originentity, where the origin entity parameter includes a real or fictitiousname and/or nickname and/or code name associated with a system 106,e.g., a telephone and/or personal computer and/or personal digitalassistant, associated with the origin entity 102.

The storing of operation 600 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 602 illustrates storing the communications context identifier,wherein the origin entity parameter includes a telephone numberassociated with the identity of the origin entity. Operation 602 mayinclude, for example, storing the communications context identifier,wherein the origin entity parameter includes a telephone numberassociated with the identity of the origin entity, where the originentity parameter includes a real or fictitious telephone numberassociated with a system 106, e.g., a telephone and/or personal computerand/or personal digital assistant, associated with the origin entity102.

The storing of operation 602 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 604 depicts storing the communications context identifier,wherein the origin entity parameter includes an Internet Protocoladdress associated with the identity of the origin entity. Operation 604may include, for instance, storing the communications contextidentifier, wherein the origin entity parameter includes an InternetProtocol address associated with the identity of the origin entity,where the origin entity parameter includes a real or fictitious InternetProtocol address associated with a system 106, e.g., a personalcomputer, associated with the origin entity 102 and used by the originentity 102 for VoIP calls and/or emailing and/or instant messaging.

The storing of operation 604 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

Operation 606 shows storing the communications context identifier,wherein the origin entity parameter includes an electronic mail addressassociated with the identity of the origin entity. Operation 606 mayinclude, for example, storing the communications context identifier,wherein the origin entity parameter includes an electronic mail addressassociated with the identity of the origin entity, where the targetentity parameter includes a real or fictitious email address associatedwith an origin entity 102.

The storing of operation 606 may be performed, e.g., upon initiation bythe origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using memory resources of the system 106 associated with theorigin entity 102 and/or the memory resources of a system and/or systemsassociated with the system 106 associated with the origin entity 102.

FIG. 7 depicts a high-level logic flowchart of an operational process.The depicted process may include one or more of the followingoperations: 200 (described elsewhere herein), 202 (described elsewhereherein), and/or 700.

Operation 700 depicts displaying the communications context parameterand/or the communications context identifier in conjunction with thecommunications context. Operation 700 may include, for example,displaying the communications context parameter and/or thecommunications context identifier in conjunction with the communicationscontext, such as displaying one or more target entity parameters, e.g.,a telephone number, name, address, etc., on the caller identificationfeature of a system 106, such as a telephone, associated with an originentity 102, in conjunction with a communication, e.g., a telephone callfrom a target entity 104 to an origin entity 102. Alternatively and/orin conjunction with the foregoing, operation 700 may include, forexample, displaying one or more origin entity parameters, e.g., a faketelephone number, name, and/or location (e.g., physical location), etc.that were previously generated responsive to the one or more targetentity parameters (e.g., such as might be used by undercover lawenforcement), on the caller identification feature of a system 106, suchas a telephone, associated with an origin entity 102, in conjunctionwith a communication, e.g., a telephone call between a target entity 104to an origin entity 102.

The displaying of operation 700 may be performed, e.g., upon initiationby the origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using one or more display features and/orhardware/software/firmware of the system 106 associated with the originentity 102.

FIGS. 8A-8B depicts several alternative implementations of thehigh-level logic flowchart of FIG. 7. Operation 700—displaying thecommunications context parameter and/or the communications contextidentifier in conjunction with the communications context—may includeone or more of the following operations: 800, 802, 804, 806, 808, 810,and/or 812.

Operation 800 depicts displaying the communications context parameterand/or the communications context identifier in a system associated withthe origin entity. Operation 800 may include, for instance, displayingthe communications context parameter and/or the communications contextidentifier in a system associated with the origin entity, such asdisplaying one or more communications context parameters including oneor more target entity parameters and/or the one or more communicationscontext identifiers including one or more origin entity parameters on adisplay feature of a system 106 associated with an origin entity 102,such as a personal digital assistant used by the origin entity 102 tosend and receive text messages. Operation 800 may also include, forinstance, displaying one or more communications context identifiersincluding one or more origin entire parameters associated with one ormore communications context parameters including one or more targetentity parameters; for example, displaying an origin-entity name,origin-entity occupation, origin-entity phone number, origin-entityemail address, etc. in conjunction with a target-entity name,target-entity occupation, target-entity phone number, target-entityemail address, etc. (e.g., such as origin entity 102 might have given totarget entity 104 when the two met at a defined location in space and/ortime (e.g., at a bar and/or in cyberspace on a particular date)). Theone or more communications context identifiers including one or moreorigin entity parameters and/or one or more communications contextparameters including one or more target entity parameters may bedisplayed on a display feature of a system 106 associated with theorigin entity 102, such as the caller ID display of a telephone.

The displaying of operation 800 may be performed, e.g., upon initiationby the origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using one or more display features and/orhardware/software/firmware of the system 106 associated with the originentity 102.

Operation 802 illustrates displaying the communications contextparameter and/or the communications context identifier in conjunctionwith an original communication. Operation 802 may include, for instance,displaying the communications context parameter and/or thecommunications context identifier in conjunction with an originalcommunication, such as displaying one or more communications contextparameters including one or more target entity parameters and/or the oneor more communications context identifiers including one or more originentity parameters in conjunction with an original email (e.g., one notsent in response to a communication) sent from a target entity 104 to anorigin entity 102. Operation 802 may also include, for example,displaying one or more communications context identifiers including oneor more origin entity parameters associated with one or morecommunications context parameters including one or more target entityparameters in conjunction with an original VoIP call (e.g., one not madein response to a communication) between a target entity 104 and anorigin entity 102; for example displaying, in conjunction with anoriginal VoIP call, the name, location (e.g., space (e.g.,physical/virtual) location and/or time location), telephone number, IPaddress, electronic mail address, etc. in conjunction with the nameand/or spacetime location that are associated with target entity 104 byorigin entity 102 (e.g., such as origin entity 102 might previously havegiven out to target entity 104 at the time that origin entity 102 mettarget entity 104). For example displaying “you met John Smith(exemplary of a name associated with target entity 104) at Starbucks inWashington D.C. (exemplary of a space location associated with targetentity 104) on 12 Sep. 2006 (exemplary of a time location associatedwith target entity 104), and at that time you told him that your namewas Mark Hamilton, that you lived in Maryland, and that you worked as acarpenter, and that your VoIP number was 111-111-1111 (exemplary of anorigin entity 102 name, location (space-time), and phone numberassociated with a target entity 102 name and space-time location as setforth in the foregoing).”

The displaying of operation 802 may be performed, e.g., upon initiationby the origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using one or more display features and/orhardware/software/firmware of the system 106 associated with the originentity 102.

Operation 804 shows displaying the communications context parameterand/or the communications context identifier in conjunction with a replycommunication in response to a communication. Operation 804 may include,for example, displaying the communications context parameter and/or thecommunications context identifier in conjunction with a replycommunication in response to a communication, such as displaying one ormore communications context parameters including one or more targetentity parameters and/or one or more communications context identifiersincluding one or more origin entity parameters in conjunction with areply text message (e.g., a text message sent in reply to a previouscommunication) between a target entity 104 and an origin entity 102.Operation 804 may also include, for instance, displaying one or morecommunications context identifiers including one or more origin entityparameters in conjunction with one or more communications contextparameters including one or more target entity parameters in conjunctionwith a reply voicemail message between a target entity 104 and an originentity 102; for example, displaying, in conjunction with a voicemailmessage, a spurious origin-entity phone number of origin entity 102 inassociation with an identity, location (e.g., space and/or time), role,phone number, etc. of target entity 104 (e.g., such as origin entity 102might have given target entity 104 in the context of a businessmeeting).

The displaying of operation 804 may be performed, e.g., upon initiationby the origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using one or more display features and/orhardware/software/firmware of the system 106 associated with the originentity 102.

Operation 806 depicts displaying the communications context parameterand/or the communications context identifier, wherein the displayingincludes displaying data associated with a telephone call. Operation 806may include, for instance, displaying the communications contextparameter and/or the communications context identifier, wherein thedisplaying includes displaying data associated with a telephone call,such as displaying one or more communications context parametersincluding one or more target entity parameters and/or one or morecommunications context identifiers including one or more origin entityparameters in conjunction with a telephone number associated with thetarget entity 104 during a telephone call and/or a VoIP call between thetarget entity 104 and the origin entity 102, where the displaying uses acaller identification feature of a system 106, e.g., a telephone and/ora VoIP endpoint, associated with the origin entity 102. Operation 806may also include, for example, displaying the communications contextparameter and/or the communications context identifier, wherein thedisplaying includes displaying data associated with a telephone call,such as displaying, in the context of a VoIP call between origin entity102 and target entity 104, a fictitious origin-entity IP address thatthe origin entity 102 had previously associated with an IP address oftarget entity 104 and that system 106 is presenting to target entity 104(e.g., allowing origin entity 102 to determine what he/she “looks like”to target entity 104). The communications context identifier includingone or more origin entity parameters may be tied to one or morecommunications context parameters including one or more target entityparameters and may be displayed on a display feature of a system 106associated with the origin entity 102, such as the display screen of acell phone.

The displaying of operation 806 may be performed, e.g., upon initiationby the origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using one or more display features and/orhardware/software/firmware are of the system 106 associated with theorigin entity 102.

Operation 808 depicts displaying the communications context parameterand/or the communications context identifier, wherein the displayingincludes displaying data associated with an instant message. Operation808 may include, for instance, displaying the communications contextparameter and/or the communications context identifier, wherein thedisplaying includes displaying data associated with an instant message,such as displaying one or more communications context parametersincluding one or more target entity parameters and/or one or morecommunications context identifiers including one or more origin entityparameters in conjunction with an instant message between the targetentity 104 and the origin entity 102. For example, displaying a nicknameassociated with the target entity 104 in conjunction with an instantmessage between the target entity 104 and the origin entity 102, wherethe nickname is displayed using the display screen of a system 106,e.g., a laptop computer, associated with the origin entity 102.Operation 808 may also include, for example, displaying thecommunications context parameter and/or the communications contextidentifier, wherein the displaying includes displaying data associatedwith an instant message, such as displaying a specialized origin-entitynickname that the origin entity 102 had previously associated with an IPaddress of target entity 104 for the purpose of misleading the targetentity 104 in, e.g., a law enforcement operation, so that the originentity 102 may verify the nickname (e.g., allowing origin entity 102 todetermine what he/she “looks like” to target entity 104). Thecommunications context identifier including one or more origin entityparameters may be tied to one or more communications context parametersincluding one or more target entity parameters and may be displayed on adisplay feature of a system 106 associated with the origin entity 102,such as the display screen of a personal computer.

The displaying of operation 808 may be performed, e.g., upon initiationby the origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using one or more display features and/orhardware/software/firmware of the system 106 associated with the originentity 102.

Operation 810 illustrates displaying the communications contextparameter and/or the communications context identifier, wherein thedisplaying includes displaying data associated with a text message.Operation 810 may include, for example, displaying the communicationscontext parameter and/or the communications context identifier, whereinthe displaying includes displaying data associated with a text message,such as displaying one or more communications context parametersincluding one or more target entity parameters and/or one or morecommunications context identifiers including one or more origin entityparameters in conjunction with an alphanumeric code related to a textmessage between the target entity 104 and the origin entity 102, wherethe alphanumeric code is displayed using the display screen of a system106, e.g., a personal digital assistant, associated with the originentity 102. Operation 810 may also include, for instance, displaying thecommunications context parameter and/or the communications contextidentifier, wherein the displaying includes displaying data associatedwith a text message, such as displaying, in the context of a textmessage between origin entity 102 and target entity 104, an actual butmisleading origin-entity telephone number associated with the originentity 102 (e.g., a telephone number for a system 106 associated withorigin entity 102), where the origin entity 102 had previouslyassociated the system identifier with an identity of the target entity104, so that the origin entity 102 may verify the origin-entitytelephone number that is being presented to target entity 104.

The displaying of operation 810 may be performed, e.g., upon initiationby the origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using one or more display features and/orhardware/software/firmware of the system 106 associated with the originentity 102.

Operation 812 shows displaying the communications context parameterand/or the communications context identifier, wherein the displayingincludes displaying data associated with an electronic mail message.Operation 812 may include, for instance, displaying the communicationscontext parameter and/or the communications context identifier, whereinthe displaying includes displaying data associated with an electronicmail message, such as displaying one or more communications contextparameters including one or more target entity parameters and/or one ormore communications context identifiers including one or more originentity parameters in conjunction with an email address associated withan email between the target entity 104 and the origin entity 102, wherethe email address is displayed using the display screen of a system 106,e.g., a cell phone, associated with the origin entity 102. Operation 812may also include, for example, displaying the communications contextparameter and/or the communications context identifier, wherein thedisplaying includes displaying data associated with an electronic mailmessage, such as displaying in the context of an email between theorigin entity 102 and the target entity 104 a specialized origin-entityemail address that the origin entity 102 had previously associated withan email address of the target entity 104, so that the origin entity 102may verify the specialized origin-entity email address previouslyassociated with the email address of the target entity 104.

The displaying of operation 812 may be performed, e.g., upon initiationby the origin entity 102 and/or upon initiation by automated action ofhardware/software/firmware of a system 106 associated with the originentity 102 and/or by hardware/software/firmware of a system and/orsystems operably coupled to the system 106 associated with the originentity 102, using one or more display features and/orhardware/software/firmware of the system 106 associated with the originentity 102.

FIG. 9 depicts a high-level logic flowchart of an operational process.The depicted process may include one or more of the followingoperations: 200 (described elsewhere herein), 202 (described elsewhereherein), and/or 900.

Operation 900 depicts transmitting the communications context identifierin conjunction with the communications context. Operation 900 mayinclude, for instance, transmitting the communications contextidentifier in conjunction with the communications context, such astransmitting an origin entity parameter, e.g., an Internet Protocoladdress, on a display feature of a system 106, such as a personalcomputer display screen, associated with an origin entity 102, inconjunction with a communication, e.g., a VoIP call from a target entity104 to an origin entity 102. Further, use of the communications contextidentifier transmitted in conjunction with the communications contextmay give rise to a display feature of a system 106 associated with theorigin entity 102, e.g., initiating the display of text and/or graphicsdenoting the communications context identifier on a display system of asystem 106 associated with the origin entity 102, for purposes of, e.g.,verifying the communications context identifier transmitted, and/orinforming and/or deceiving entities proximate to or associated with theorigin entity 102. Such use of the communications context identifiertransmitted in conjunction with the communications context may give riseto a display feature, e.g., in conjunction with an originalcommunication, in conjunction with a reply communication in response toan incoming communication, in conjunction with transmitting dataassociated with a telephone call, in conjunction with transmitting dataassociated with an instant message, in conjunction with transmittingdata associated with a text message, and/or in conjunction withtransmitting data associated with an electronic mal message.

The transmitting of operation 900 may be performed, e.g., uponinitiation by the origin entity 102 and/or upon initiation by automatedaction of hardware/software/firmware of a system 106 associated with theorigin entity 102 and/or by hardware/software/firmware of a systemand/or systems operably coupled to the system 106 associated with theorigin entity 102, using hardware/software/firmware of the system 106associated with the origin entity 102.

FIG. 10 depicts several alternative implementations of the high-levellogic flowchart of FIG. 9. Operation 900—transmitting the communicationscontext identifier in conjunction with the communications context—mayinclude one or more of the following operations: 1000, 1002, 1004, 1006,1008, and/or 1010.

Operation 1000 depicts transmitting the communications contextidentifier in conjunction with an original communication. Operation 1000may include, for example, transmitting the communications contextidentifier in conjunction with an original communication, such astransmitting a communications context parameter including a targetentity parameter in conjunction with an original instant message (e.g.,one not sent in response to a communication) sent from an origin entity102 to a target entity 104, using a system 106, e.g., a laptop computer,associated with the origin entity 102.

The transmitting of operation 1000 may be performed, e.g., uponinitiation by the origin entity 102 and/or upon initiation by automatedaction of hardware/software/firmware of a system 106 associated with theorigin entity 102 and/or by hardware/software/firmware of a systemand/or systems operably coupled to the system 106 associated with theorigin entity 102, using hardware/software/firmware of the system 106associated with the origin entity 102.

Operation 1002 illustrates transmitting the communications contextidentifier in conjunction with a reply communication in response to anincoming communication. Operation 1002 may include, for example,transmitting the communications context identifier in conjunction with areply communication in response to an incoming communication, such as acommunications context parameter including a target entity parameter inconjunction with a reply VoIP call (e.g., a VoIP call made in reply to aprevious communication) from an origin entity 102 to a target entity104, using system 106, e.g., a personal computer, associated with theorigin entity 102.

The transmitting of operation 1002 may be performed, e.g., uponinitiation by the origin entity 102 and/or upon initiation by automatedaction of hardware/software/firmware of a system 106 associated with theorigin entity 102 and/or by hardware/software/firmware of a systemand/or systems operably coupled to the system 106 associated with theorigin entity 102, using hardware/software/firmware of the system 106associated with the origin entity 102.

Operation 1004 illustrates transmitting the communications contextidentifier, wherein the transmitting includes transmitting dataassociated with a telephone call. Operation 1004 may include, forexample, transmitting the communications context identifier, wherein thetransmitting includes transmitting data associated with a telephonecall, such as a nickname associated with the origin entity 102 inconjunction with a telephone call and/or a VoIP call from the originentity 102 to the target entity 104, using a system 106, e.g., atelephone or a Von′ endpoint, associated with the origin entity 102.

The transmitting of operation 1004 may be performed, e.g., uponinitiation by the origin entity 102 and/or upon initiation by automatedaction of hardware/software/firmware of a system 106 associated with theorigin entity 102 and/or by hardware/software/firmware of a systemand/or systems operably coupled to the system 106 associated with theorigin entity 102, using hardware/software/firmware of the system 106associated with the origin entity 102.

Operation 1006 shows transmitting the communications context identifier,wherein the transmitting includes transmitting data associated with aninstant message. Operation 1006 may include, for instance, transmittingthe communications context identifier, wherein the transmitting includestransmitting data associated with an instant message, such as a nicknameassociated with the origin entity 102 in conjunction with an instantmessage sent from the origin entity 102 to the target entity 104, usinga system 106, e.g., a laptop computer, associated with the origin entity102.

The transmitting of operation 1006 may be performed, e.g., uponinitiation by the origin entity 102 and/or upon initiation by automatedaction of hardware/software/firmware of a system 106 associated with theorigin entity 102 and/or by hardware/software/firmware of a systemand/or systems operably coupled to the system 106 associated with theorigin entity 102, using hardware/software/firmware of the system 106associated with the origin entity 102.

Operation 1008 depicts transmitting the communications contextidentifier, wherein the transmitting includes transmitting dataassociated with a text message. Operation 1008 may include, for example,transmitting the communications context identifier, wherein thetransmitting includes transmitting data associated with a text message,such as a code name associated with the origin entity 102 in conjunctionwith a text message sent from the origin entity 102 to the target entity104, using a system 106, e.g., a personal digital assistant, associatedwith the origin entity 102.

The transmitting of operation 1008 may be performed, e.g., uponinitiation by the origin entity 102 and/or upon initiation by automatedaction of hardware/software/firmware of a system 106 associated with theorigin entity 102 and/or by hardware/software/firmware of a systemand/or systems operably coupled to the system 106 associated with theorigin entity 102, using hardware/software/firmware of the system 106associated with the origin entity 102.

Operation 1010 shows transmitting the communications context identifier,wherein the transmitting includes transmitting data associated with anelectronic mail message. Operation 1010 may include, for instance,transmitting the communications context identifier, wherein thetransmitting includes transmitting data associated with an electronicmail message, such as an email address associated with the origin entity102 in conjunction with an email from the origin entity 102 to thetarget entity 104, using a system 106, e.g., a laptop computer,associated with the origin entity 102.

The transmitting of operation 1010 may be performed, e.g., uponinitiation by the origin entity 102 and/or upon initiation by automatedaction of hardware/software/firmware of a system 106 associated with theorigin entity 102 and/or by hardware/software/firmware of a systemand/or systems operably coupled to the system 106 associated with theorigin entity 102, using hardware/software/firmware of the system 106associated with the origin entity 102.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and/or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (Asics), FieldProgrammable Gate Arrays (Fogs), digital signal processors (Dips), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and/or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies equally regardless of the particular type of signal bearingmedia used to actually carry out the distribution. Examples of a signalbearing medium include, but are not limited to, the following: arecordable type medium such as a floppy disk, a hard disk drive, aCompact Disc (CD), a Digital Video Disk (DVD), a digital tape, acomputer memory, etc.; and a transmission type medium such as a digitaland/or an analog communication medium (e.g., a fiber optic cable, awaveguide, a wired communications link, a wireless communication link,etc.).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment). Those having skill in the art will recognize that thesubject matter described herein may be implemented in an analog ordigital fashion or some combination thereof.

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use engineering practices to integrate such describeddevices and/or processes into image processing systems. That is, atleast a portion of the devices and/or processes described herein can beintegrated into an image processing system via a reasonable amount ofexperimentation. Those having skill in the art will recognize that atypical image processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, and applications programs, one or more interaction devices,such as a touch pad or screen, control systems including feedback loopsand control motors (e.g., feedback for sensing lens position and/orvelocity; control motors for moving/distorting lenses to give desiredfocuses. A typical image processing system may be implemented utilizingany suitable commercially available components, such as those typicallyfound in digital still systems and/or digital motion systems.

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use engineering practices to integrate such describeddevices and/or processes into data processing systems. That is, at leasta portion of the devices and/or processes described herein can beintegrated into a data processing system via a reasonable amount ofexperimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors (e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities). A typical data processingsystem may be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

All of the above U.S. patents, U.S. patent application publications,U.S. patent applications, foreign patents, foreign patent applicationsand non-patent publications referred to in this specification and/orlisted in any Application Data Sheet, are incorporated herein byreference, in their entireties.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of this subject matter describedherein. Furthermore, it is to be understood that the invention isdefined by the appended claims. It will be understood by those withinthe art that, in general, terms used herein, and especially in theappended claims (e.g., bodies of the appended claims) are generallyintended as “open” terms (e.g., the term “including” should beinterpreted as “including but not limited to,” the term “having” shouldbe interpreted as “having at least,” the term “includes” should beinterpreted as “includes but is not limited to,” etc.). It will befurther understood by those within the art that if a specific number ofan introduced claim recitation is intended, such an intent will beexplicitly recited in the claim, and in the absence of such recitationno such intent is present. For example, as an aid to understanding, thefollowing appended claims may contain usage of the introductory phrases“at least one” and “one or more” to introduce claim recitations.However, the use of such phrases should not be construed to imply thatthe introduction of a claim recitation by the indefinite articles “a” or“an” limits any particular claim containing such introduced claimrecitation to inventions containing only one such recitation, even whenthe same claim includes the introductory phrases “one or more” or “atleast one” and indefinite articles such as “a” or “an” (e.g., “a” and/or“an” should typically be interpreted to mean “at least one” or “one ormore”); the same holds true for the use of definite articles used tointroduce claim recitations. In addition, even if a specific number ofan introduced claim recitation is explicitly recited, those skilled inthe art will recognize that such recitation should typically beinterpreted to mean at least the recited number (e.g., the barerecitation of “two recitations,” without other modifiers, typicallymeans at least two recitations, or two or more recitations).Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.).

While various aspects and embodiments have been disclosed herein, otheraspects and embodiments will be apparent to those skilled in the art.The various aspects and embodiments disclosed herein are for purposes ofillustration and are not intended to be limiting, with the true scopeand spirit being indicated by the following claims.

We claim:
 1. A method related to communication, the method comprising:storing a communications context parameter associated with acommunications context; and storing a communications context identifierassociated with the communications context.
 2. The method of claim 1,wherein the storing a communications context parameter associated with acommunications context further comprises: storing the communicationscontext parameter, wherein the communications context parameter includesa target entity parameter associated with a location associated with atarget entity.
 3. The method of claim 1, wherein the storing acommunications context parameter associated with a communicationscontext further comprises: storing the communications context parameter,wherein the communications context parameter includes a target entityparameter associated with a system associated with the target entity. 4.The method of claim 1, wherein the storing a communications contextparameter associated with a communications context further comprises:storing the communications context parameter, wherein the communicationscontext parameter includes a target entity parameter associated with anidentity of a target entity.
 5. The method of claim 4, wherein thestoring the communications context parameter, wherein the communicationscontext parameter includes a target entity parameter associated with anidentity of a target entity further comprises: storing thecommunications context parameter, wherein the target entity parameterincludes a name associated with the identity of the target entity. 6.The method of claim 4, wherein the storing the communications contextparameter, wherein the communications context parameter includes atarget entity parameter associated with an identity of a target entityfurther comprises: storing the communications context parameter, whereinthe target entity parameter includes a telephone number associated withthe identity of the target entity.
 7. The method of claim 4, wherein thestoring the communications context parameter, wherein the communicationscontext parameter includes a target entity parameter associated with anidentity of a target entity further comprises: storing thecommunications context parameter, wherein the target entity parameterincludes an Internet Protocol address associated with the identity ofthe target entity.
 8. The method of claim 4, wherein the storing thecommunications context parameter, wherein the communications contextparameter includes a target entity parameter associated with an identityof a target entity further comprises: storing the communications contextparameter, wherein the target entity parameter includes an electronicmail address associated with the identity of the target entity.
 9. Themethod of claim 1, wherein the storing a communications contextparameter associated with a communications context further comprises:storing the communications context parameter, wherein at least a portionof the communications context parameter is randomly generated.
 10. Themethod of claim 1, wherein the storing a communications contextparameter associated with a communications context further comprises:storing the communications context parameter, wherein at least a portionof the communications context parameter is pseudo-randomly generated.11. The method of claim 1, wherein the storing a communications contextparameter associated with a communications context further comprises:storing the communications context parameter, wherein at least a portionof the target entity parameter is selected from a database.
 12. Themethod of claim 1, wherein the storing a communications contextparameter associated with a communications context further comprises:storing the communications context parameter, wherein the communicationscontext parameter may be displayed in conjunction with a communicationin the communications context.
 13. The method of claim 1, wherein thestoring a communications context identifier associated with thecommunications context further comprises: storing the communicationscontext identifier, wherein the communications context identifierincludes an origin entity parameter associated with a location of anorigin entity.
 14. The method of claim 1, wherein the storing acommunications context identifier associated with the communicationscontext further comprises: storing the communications contextidentifier, wherein the communications context identifier includes anorigin entity parameter associated with a system of an origin entity.15. The method of claim 1, wherein the storing a communications contextidentifier associated with the communications context further comprises:storing the communications context identifier, wherein thecommunications context identifier includes an origin entity parameterassociated with an identity an origin entity.
 16. The method of claim15, wherein the storing the communications context identifier, whereinthe communications context identifier includes an origin entityparameter associated with an identity of an origin entity furthercomprises: storing the communications context identifier, wherein theorigin entity parameter includes a name associated with the identity ofthe origin entity.
 17. The method of claim 15, wherein the storing thecommunications context identifier, wherein the communications contextidentifier includes an origin entity parameter associated with anidentity of an origin entity further comprises: storing thecommunications context identifier, wherein the origin entity parameterincludes a telephone number associated with the identity of the originentity.
 18. The method of claim 15, wherein the storing thecommunications context identifier, wherein the communications contextidentifier includes an origin entity parameter associated with anidentity of an origin entity further comprises: storing thecommunications context identifier, wherein the origin entity parameterincludes an Internet Protocol address associated with the identity ofthe origin entity.
 19. The method of claim 15, wherein the storing thecommunications context identifier, wherein the communications contextidentifier includes an origin entity parameter associated with anidentity of an origin entity further comprises: storing thecommunications context identifier, wherein the origin entity parameterincludes an electronic mail address associated with the identity of theorigin entity.
 20. The method of claim 1, wherein the storing acommunications context identifier associated with the communicationscontext further comprises: storing the communications contextidentifier, wherein at least a portion of the communications contextidentifier is randomly generated.